-
Notifications
You must be signed in to change notification settings - Fork 766
update datasource connection when manually introspecting #6968
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update datasource connection when manually introspecting #6968
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Breaking changes detected in the OpenAPI specification! |
f9bac28 to
5724bdc
Compare
|
Breaking changes detected in the OpenAPI specification! |
|
not sure why the spec is failing. |
|
Breaking changes detected in the OpenAPI specification! |
c906ae6 to
999dc1c
Compare
|
Breaking changes detected in the OpenAPI specification! |
999dc1c to
9ecf1ed
Compare
|
Breaking changes detected in the OpenAPI specification! |
9ecf1ed to
482ae68
Compare
|
Breaking changes detected in the OpenAPI specification! |
482ae68 to
51e6b24
Compare
|
Breaking changes detected in the OpenAPI specification! |
mscolnick
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just FYI, this perf is not bad (as you said its m + n), but it could be O(1) if we do find it becomes an issue
📝 Summary
Upon introspecting the database on the left-hand panel, we receive the messages and update the datasource connection, therefore ensuring autocompletions and context are loaded for AI or editing.
Added perf tests to see the impact, and it was very fast due to how db's are hierarchied. O(m+n+p), m < n < p.
Avg time is 0.0033ms on large hierarchy
🔍 Description of Changes
📋 Checklist